perm filename LETTER.TXT[1,RWF]1 blob
sn#823820 filedate 1986-08-29 generic text, type C, neo UTF8
COMMENT ā VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002
C00005 ENDMK
Cā;
A page width of 80 characters like this one requires large lateral eye motions,
and it is hard to find the right line at the end of the backscan. I have been
told that it is good editorial practice to use no more than 70 characters per
line, and to me it seems about right. Is there some way that most BBOARD
messages could be put into a narrower format? For example, using a default line
width of 50 characters for EMAIL editing, or running most messages through a
reformatter when they are entered into BBOARDs. The following paragraph is this
one in a narrower format. This is 80 wide.
A page width of 80 characters like this one
requires large lateral eye motions, and it is hard
to find the right line at the end of the backscan.
I have been told that it is good editorial
practice to use no more than 70 characters per
line, and to me it seems about right. Is there
some way that most BBOARD messages could be put
into a narrower format? For example, using a
default line width of 50 characters for EMAIL
editing, or running most messages through a
reformatter when they are entered into BBOARDs.
The following paragraph is this one in a narrower
format. This is 50 wide.
A page width of 80 characters like this
on requires large lateral eye motions,
and it is hard to find the right line at
the end of the backscan. I have been
told that it is good editorial practice
to use no more than 70 characters per
line, and to me it seems about right.
Is there some way that most BBOARD
messages could be put into a narrower
format? For example, using a default
line width of 50 characters for EMAIL
editing, or running most messages
through a reformatter when they are
entered into BBOARDs. The following
paragraph is this one in a narrower
format. This is 40 wide.